Ancillary Data Integration Error and Warning Messages
Learn about the error and warning messages related to the Ancillary Data Integration process, as displayed in the process log, along with their resolutions.
| Type | Message | Cause and Resolution |
|---|---|---|
| Error | Please specify a valid ancillary data file. | This error occurs when you do not provide an ancillary data file path, or the path is empty or contains only whitespace. To resolve this error, specify a valid ancillary data file (.csv, .xls, or .xlsx). |
| Error | The specified ancillary data file does not exist. | This error occurs when the file path provided does not point to an existing file in Cobra. To resolve this error, verify that the file path exists and is accessible. |
| Error | The ancillary data file path contains invalid characters. | This error occurs when the file path contains characters that are not allowed in file paths. To resolve this error, remove the invalid characters from the file path. |
| Error | The ancillary data file must be a .CSV, .XLS, or .XLSX file. | This error occurs when the selected file does not have a supported file extension. To resolve this error, use a .csv, .xls, or .xlsx file format. |
| Error | Please select a valid Cobra filename. | This error occurs when you do not select a Cobra file (calendar, code, resource, or rate). To resolve this error, select a valid Cobra filename from the available options. |
| Error | The selected calendar file does not exist. | This error occurs when the selected calendar file does not exist in Cobra. To resolve this error, create the calendar file first or select an existing one. |
| Error | The selected code file does not exist. | This error occurs when the selected code file does not exist in Cobra. To resolve this error, create the code file first or select an existing one. |
| Error | The selected resource file does not exist. | This error occurs when the selected resource file does not exist in Cobra. To resolve this error, create the resource file first or select an existing one. |
| Error | The selected rate file does not exist. | This error occurs when the selected rate file does not exist in Cobra. To resolve this error, create the rate file first or select an existing one. |
| Error | You have insufficient rights to perform this action on {0} file ‘{1}’. | This error occurs when you do not have write access to the selected calendar, code, resource, or rate file. To resolve this error, contact your Cobra administrator to request write access to the file. |
| Error | The following field mapper columns are duplicated. | This error occurs when you map multiple source columns to the same Cobra field, which is not allowed. To resolve this error, ensure each Cobra field is mapped to only one source column or use a default value for unmapped columns. |
| Error | The field Period Date is required for calendar import. | This error occurs when you import a calendar that requires the FSC_DATE field to be mapped. To resolve this error, map a source column to the “Period Date” (FSC_DATE) field. |
| Error | The field Code is required for codes import. | This error occurs when you import code data that requires the CODE field to be mapped. To resolve this error, map a source column to the “Code” (CODE) field. |
| Error | The field Resource is required for resources import. | This error occurs when you import resource data that requires the CECODE field to be mapped. To resolve this error, map a source column to the “Resource ID” (CECODE) field. |
| Error | The field Resource is required for resource calculations import. | This error occurs when you import resource calculation data that requires the CECODE field to be mapped. To resolve this error, map a source column to the “Resource ID” (CECODE) field. |
| Error | The field Field Name is required for resource calculations import. | This error occurs when you import resource calculation data that requires the RESULT field to be mapped. To resolve this error, map a source column to the “Field Name” (RESULT) field. |
| Error | The field Line is required for resource calculations import. | This error occurs when you import resource calculation data that requires the LINE field to be mapped. To resolve this error, map a source column to the “Line” (LINE) field. |
| Error | The field Rate Set is required for rates import. | This error occurs when you import rate data that requires the RATE_TABLE field to be mapped. To resolve this error, map a source column to the “Rate Set” (RATE_TABLE) field. |
| Error | The field Rate Date is required for rates import. | This error occurs when you import rate data that requires the RATE_DATE field to be mapped. To resolve this error, map a source column to the “Rate Date” (RATE_DATE) field. |
| Error | The field Holiday Date is required for holidays import. | This error occurs when you import holiday data that requires the HOLIDAY field to be mapped. To resolve this error, map a source column to the “Holiday Date” (HOLIDAY) field. |
| Error | Could not create file operation object. | This error occurs when the file operations factory fails to create a valid file operation object during PreExecute. To resolve this error, verify that the ancillary file type is valid and supported. Ensure that clssfile.prg and the CFileOperationsFactory class are accessible and properly initialized. |
| Error | There are records in the Import file with empty File values. These records will be ignored. | This error occurs when the import file contains records where the file field value is empty while lHasFileField is true. To resolve this error, ensure all records in the import file have valid file field values if file field mapping is enabled. Invalid records are automatically skipped. |
| Error | You must have update rights to import codes into the code file ‘{0}’. | This error occurs when you do not have update access (FILE_RIGHTS) for the specified breakdown file. To resolve this error, contact your Cobra administrator to request update access to the breakdown file or have the Cobra administrator perform the import. |
| Error | The Code file ‘{0}’ being loaded does not exist. | This error occurs when lHasFileField is true and the code file specified in the import data is not found in the header table. To resolve this error, verify that the file name in the import file matches existing code files in Cobra or create the code file before importing. |
| Error | Could not get exclusive use of Breakdown Structure {0}. | This error occurs when another user or process has the breakdown structure file locked. To resolve this error, ensure no other users are accessing the breakdown structure file. Close any dialog boxes or processes using the file, then retry the import. |
| Error | The import file {0} does not exist. | This error occurs when the specified source file path does not exist in Cobra. To resolve this error, verify that the source file path is correct and the file exists at that location. Check the file permissions and network paths, if applicable. |
| Error | Error opening destination tables. | This error occurs when there is a database connection failure or invalid table names when Cobra attempts to open header, description, or detail tables. To resolve this error, verify database connectivity, check that all required tables exist, ensure proper permissions, and review the database connection settings. |
| Error | Error importing file. Check that the file is of correct type and try again. | This error occurs when a file parsing error occurs during the APPEND FROM operation. To resolve this error, verify that the file type matches the selected import type (Excel, .csv, and so on), check the file for corruption, and ensure the file format is compatible with Cobra import. |
| Error | The import file is empty. | This error occurs when, after you load the source file into the IMP cursor and applying filters, no records remain. To resolve this error, verify that the import file contains data, confirm that field mappings are correct, and ensure that data is not being filtered out during the load process. |
| Error | Compulsory field {0} is not defined. | This error occurs when a required field from the aCompulsoryFields array does not exist in the IMP cursor. To resolve this error, ensure all compulsory fields are mapped in the import definition and verify that the source file contains columns for all required fields. |
| Error | The compulsory field(s) {0} are empty (Record {1}). | This error occurs when one or more required fields have empty values in a record. To resolve this error, populate all required fields in the import file and review the record numbers listed in the error messages to correct the source data. |
| Error | The compulsory field(s) {0} have leading spaces (Record {1}). | This error occurs when the character compulsory fields contain leading spaces. To resolve this error, remove leading spaces from the compulsory field values in the source data and trim or clean the data before importing. |
| Error | Duplicate found for ‘{0}’ (Records {1}). | This error occurs when multiple records have identical key field combinations. To resolve this error, remove duplicate records from the ancillary data file, ensure each record has a unique key field combination, and review the listed record numbers to correct the data. |
| Error | Could not select the Import table. | This error occurs when the IMP cursor is not open or available when validation methods attempt to select it. To resolve this error, verify that temporary table creation succeeded, check for file access issues, and review the memory constraints that may prevent cursor creation. |
| Error | The result {0} contains invalid characters. (Record {1}). | This error occurs when the RESULT field contains characters that are not allowed in Cobra identifiers. To resolve this error, remove or replace invalid characters in the RESULT field. Use only alphanumeric characters, underscores, and hyphens. |
| Error | Error updating {0} file: {1}. | This error occurs when SQLTABLEUPDATE() fails while saving the header record or when it fails for the description view or detail table during SaveTemporaryTables. To resolve this error, review the database error details, check constraints, triggers, and permissions, verify data integrity and validity, and then retry the import. |
| Error | SQL Error deleting {0}. | This error occurs when a Pass-through SQL DELETE fails while deleting description or detail records during an overwrite operation or when an SQL SELECT COUNT fails while counting records for deletion tracking during the same operation. To resolve this error, check the database connectivity, verify that constraints allow deletion, ensure no foreign key restrictions are blocking the operation, and review permissions for both SELECT and DELETE operations. |
| Error | Unable to locate the {0} ‘{1}’, the {0} may be invalid. | This error occurs when the CanOverwriteAllRecords validation fails because the ancillary file is either missing from Cobra or invalid. To resolve this error, verify that the ancillary file exists in Cobra before attempting import and check the file name for spelling and case sensitivity. |
| Error | Element of Cost file not selected. | This error occurs when CostElemFile is empty during validation of resource codes that require an element-of-cost mapping. To resolve this error, select an Element of Cost file (EOC) in the import settings when you use EOC field validation. |
| Error | Resource code file not selected. | This error occurs when ResourceCodeFile is empty during resource code validation. To resolve this error, select a Resource Code file in the import settings when you use EOC field validation. |
| Error | Resource codes not imported. | This error occurs when no resource code file is selected or configured during resource data import. To resolve this error, configure a resource code file in the import settings before importing resource data. |
| Error | Code file {0} not found. | This error occurs when the breakdown code file specified in the CODEFILES field does not exist in Cobra. To resolve this error, verify that the code file exists in Cobra and check the spelling and case of the code file name in the import data. |
| Error | Code field ‘{0}’ does not allow empty values. | This error occurs when the code field has validation criteria CODES_VALIDATE_YES but its value is empty. To resolve this error, provide a value for all code fields with validation set to Yes and review code field requirements to ensure mandatory fields are populated. |
| Error | Code field ‘{0}’ does not allow value {1}. | This error occurs when the code value is not found in the associated code file during validation. To resolve this error, verify that the code value exists in the referenced code file and add missing codes or correct the values in the import data. |
| Error | Rate file error. | This error occurs when the rate file specified in vpcRateFile cannot be accessed or opened. To resolve this error, verify that the rate file exists and is accessible and check the file permissions and the spelling of the rate file name. |
| Error | Could not load the data from the text file. | This error occurs when the APPEND FROM command fails while loading note data from a text file into a temporary table. To resolve this error, verify that the text file format is correct, check the file encoding and delimiters, and ensure the file is not locked by another process. |
| Error | Mismatched quote found in the note import file. | This error occurs when the note text contains unmatched quotation marks. To resolve this error, review the note text for unpaired quotes, escape quotes properly or use a different delimiter, and correct the source text file formatting. |
| Error | {0} ‘{1}’ not found. | This error occurs when the control account or work package code specified in the import data does not exist in the project structure or when the code exists but has an invalid status or properties. To resolve this error, verify that the control account or work package code exists in the project, check the code spelling, ensure the codes are created before importing related data, and confirm that the code is active and properly configured for use in the given context. |
| Error | Couldn’t update the note text. | This error occurs when the SQLTABLEUPDATE command fails while updating existing note text. To resolve this error, verify the database connectivity and transaction state, check that the note record exists and is not locked, and review the database logs for errors. |
| Error | Invalid codes found during import. | This error occurs when the counter for invalid codes is greater than zero after validation. To resolve this error, review the previous error messages identifying specific invalid codes and correct the code values in the import file before retrying the import. |
| Warning | There are records in the Import file with empty File values. These records will be ignored. | This warning occurs when the import file contains records with empty file field values. To resolve this warning, ensure all records have valid file field values if file field mapping is enabled. Invalid records are automatically skipped during import. |
| Warning | The Code file ‘{0}’ being loaded does not exist. | This warning occurs when the HasFileField setting is true and the code file specified in the import data cannot be found. To resolve this warning, verify that the file name in the import matches an existing code file in Cobra or create the code file before importing. |
| Warning | The Parent wasn’t specified when loading the Non-Significant file ‘{0}’. The new codes will be loaded as a flat structure. | This warning occurs when you import into a non-significant breakdown in update mode without parent field mapping. To resolve this warning, if a hierarchical structure is needed, include the parent field in the import mapping. Otherwise, this is informational—codes will import successfully as a flat structure. |
| Warning | The Parent wasn’t specified when loading the Non-Significant file ‘{0}’. The code file will be loaded as a flat structure. | This warning occurs when a non-significant file is imported without parent field mapping in overwrite mode. To resolve this warning, include the parent field mapping if a hierarchical structure is required. |
| Warning | All entries for the compulsory field(s) {0} are empty. This could be caused by the version of the Excel spreadsheet you are importing. | This warning occurs when you import Excel 5.0 files and all mandatory date fields are empty. To resolve this warning, save the Excel spreadsheet in an earlier Excel format (for example, Excel 97-2003) and retry the import or verify that the date fields contain valid date values. |
| Warning | The threshold logic field {0} value ‘{1}’ is invalid in record {2}. This record has been changed to ‘OR’. | This warning occurs when the logic field value is neither “OR” nor “AND.” To resolve this warning, verify that logic field values are either “OR” or “AND.” The record is auto-corrected but review the source data for consistency. |
| Warning | Element of cost code {0} not found in resource code file for program {1}. | This warning occurs when the EOC code from the import file is not found in the resource code file. To resolve this warning, verify that all EOC codes in the import file exist in the resource code file. If there is an error, correct the code references or add the missing codes to the resource code file. |
| Warning | Invalid EOC value ‘{0}’ in record {1} | This warning occurs when the EOC field value does not exist in the EOC file. To resolve this warning, verify EOC values against the EOC file and add missing codes or correct the import data. |